ebab7d0da53c51438720d60c6e2e467c - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Java Business Integration</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Java Business Integration</span></span>

</h1>

</header>

<p><b>Java Business Integration</b> (<b>JBI</b>) is a specification developed under the <a href="Java_Community_Process" title="Java Community Process">Java Community Process</a> (JCP) for an approach to implementing a <a href="Service-oriented_architecture" title="Service-oriented architecture">service-oriented architecture</a> (SOA). The JCP reference is JSR 208 for JBI 1.0 and JSR 312 for JBI 2.0. JSR 312 was removed from the JCP balloting process on 17 Dec, 2010 by the submitters without being accepted.

</p><p>JBI is built on a <a href="Web_Service" class="mw-redirect" title="Web Service">Web Services</a> model and provides a pluggable architecture for a container that hosts service producer and consumer components. Services connect to the container via binding components (BC) or can be hosted inside the container as part of a service engine (SE). The services model used is <a href="Web_Services_Description_Language" title="Web Services Description Language">Web Services Description Language 2.0</a>. The central message delivery mechanism, the normalized message router (NMR), delivers normalized messages via one of four <a href="Message_Exchange_Pattern" class="mw-redirect" title="Message Exchange Pattern">Message Exchange Patterns</a> (MEPs), taken from WSDL 2.0:

</p>

<ol><li><b>In-Only</b>: A standard one-way messaging exchange where the consumer sends a message to the provider that provides only a status response.</li>

<li><b>Robust In-Only</b>: This pattern is for reliable one-way message exchanges. The consumer initiates with a message to which the provider responds with status. If the response is a status, the exchange is complete, but if the response is a fault, the consumer must respond with a status.</li>

<li><b>In-Out</b>: A standard two-way message exchange where the consumer initiates with a message, the provider responds with a message or fault and the consumer responds with a status.</li>

<li><b>In Optional-Out</b>: A standard two-way message exchange where the provider's response is optional.</li></ol>

<p>To handle functionality that deals with installation, deployment, monitoring and lifecycle concerns amongst BCs and SEs, <a href="Java_Management_Extensions" title="Java Management Extensions">Java Management Extensions</a> (JMX) is used. JBI defines standardized packaging for BCs and SEs, allowing components to be portable to any JBI implementation without modification.

</p><p>JBI defines standard packaging for composite applications: applications that are composed of service consumers and providers. Individual service units are deployable to components; groups of service units are gathered together into a service assembly. The service assembly includes metadata for "wiring" the service units together (associating service providers and consumers), as well as wiring service units to external services. This provides a simple mechanism for performing composite application assembly using services.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="JBI_implementations">JBI implementations</h2></div>

<p>The following <a href="Open-source_software" title="Open-source software">open-source software</a> JBI based <a href="Enterprise_Service_Bus" class="mw-redirect" title="Enterprise Service Bus">ESB</a> implementations are available:

</p>

<li><a href="Petals_ESB" title="Petals ESB">Petals ESB</a></li>

<li>Apache ServiceMix</li>

<li><a href="FUSE_ESB" class="mw-redirect" title="FUSE ESB">FUSE ESB</a> (enterprise ServiceMix) - compliant JSR 208</li>

<li><a href="Mule_(software)" title="Mule (software)">Mule</a>. Though not a JBI compliant container by itself, Mule provides interoperability with JBI containers. There is a separate Mule-JBI project that is to address this JBI compliance issue.</li></ul>

<p>The following ESBs are certified by the JBI/JSR 208 TCK: <a href="Open_ESB" class="mw-redirect" title="Open ESB">Open ESB</a> and <a href="Petals_ESB" title="Petals ESB">Petals ESB</a>.

</p><p>In addition, the Project <a href="GlassFish" title="GlassFish">GlassFish</a> open-source Java EE application server comes with the JBI runtime from the <a href="OpenESB" title="OpenESB">Open ESB</a> project.

</p><p><a href="Java_EE" class="mw-redirect" title="Java EE">Java EE</a> SDK also includes the JBI runtime and a <a href="BPEL" class="mw-redirect" title="BPEL">BPEL</a> orchestration engine.

</p><p>Oracle claims its Fusion Middleware comes with JBI implementation.

</p><p><a href="TIBCO" class="mw-redirect" title="TIBCO">TIBCO</a> ActiveMatrix Service Grid provides a service container framework, based on the JSR 208 and <a href="Service_component_architecture" class="mw-redirect" title="Service component architecture">SCA</a> specifications (<a href="Service_Component_Architecture" title="Service Component Architecture">Service Component Architecture</a>), allowing service containers (Java, Java EE, .net, BPEL) to be added as needed, as composite applications on a common foundation.

</p>

<div class="mw-heading mw-heading2"><h2 id="Existing_JBI_Components">Existing JBI Components</h2></div>

<p>Open JBI Components project on java.net is an incubator project started to foster community-based development of JBI components that conform to the Java Business Integration specification (JSR 208).

</p>

<div class="mw-heading mw-heading2"><h2 id="Books">Books</h2></div>

<ul><li>Binildas A. Christudas, "Service-Oriented Java Business Integration" (Packt Publishing: Feb 2008, <style data-mw-deduplicate="TemplateStyles:r1238218222">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-84719-440-0</bdi>; <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-84719-440-4</bdi>), <a rel="nofollow" class="external free" href="http://www.packtpub.com/service-oriented-java-business-integration">http://www.packtpub.com/service-oriented-java-business-integration</a></li></ul>

<ul><li><a href="Enterprise_Service_Bus" class="mw-redirect" title="Enterprise Service Bus">Enterprise Service Bus</a> solutions offered by several <a href="Java_platform" class="mw-redirect" title="Java platform">Java platform</a> vendors.</li>

<li><a href="Service_Component_Architecture" title="Service Component Architecture">Service Component Architecture</a> (SCA)</li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://coresumo.com/difference-between-c-vs-c-vs-python-vs-java/">Difference Between C vs C++ vs Python vs Java</a></span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="http://jcp.org/aboutJava/communityprocess/final/jsr208/index.html">JSR 208 specification on the JCP site</a></li>

<li><a rel="nofollow" class="external text" href="http://www.osoa.org/display/Main/Relationship+of+SCA+and+JBI">Open SOA article on JBI's relationship to SCA</a></li>

<li><a rel="nofollow" class="external text" href="https://download.oracle.com/otndocs/jcp/jbi-1_0-pfd2-spec-oth-JSpec/">Java Business Integration Specification.</a></li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-01-22" href="https://en.wikipedia.org/wiki/?title=Java_Business_Integration&oldid=1197881953">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>